Skip to content

Conversation

@gustavobascope
Copy link
Contributor

@gustavobascope gustavobascope commented Jan 28, 2026

Issue & Reproduction Steps

Submit action is not working when a new Inbox rule is created

Solution

submit button listener

How to Test

Create a simple process (start event - task - task - end event)
Create a simple screen
Add a line input control
Add a submit button
Assign this screen in both tasks
Run a Case
Fill fields
Press submit button
Run other Case
Press Create rule button when screen is displaying
Check Save and reuse filled data field
Add a date in the deactivation date field
Press Next button
Check Submit after filling field
Select a submit button on the screen

Related Tickets & Packages

https://processmaker.atlassian.net/browse/FOUR-28985


Note

Medium Risk
Touches cross-window iframe event handling and adds DOM click interception, which can be brittle (cross-origin, timing) and may affect submit behavior across embedded task previews.

Overview
Fixes cases where creating a new Inbox rule caused the Submit action to emit unusable data by adding a fallback path that captures submit-button metadata directly from the embedded task preview iframe.

InboxRuleFillData.vue now tracks the last clicked submit button (name/label/value), emits that data when formSubmit events arrive without valid button info, and hooks an iframe click listener after taskReady to populate this fallback (with a guarded cross-origin warning).

Written by Cursor Bugbot for commit f19c034. This will update automatically on new commits. Configure here.

@processmaker-sonarqube
Copy link

Quality Gate passed Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

@nolanpro nolanpro merged commit 184902c into develop Jan 29, 2026
6 of 11 checks passed
@nolanpro nolanpro deleted the bugfix/FOUR-28985 branch January 29, 2026 19:49
Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

This is the final PR Bugbot will review for you during this billing cycle

Your free Bugbot reviews will reset on February 21

Details

Your team is on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle for each member of your team.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

reload() {
this.formData = {};
this.iframeContentWindow.location.reload();
},
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Stale button data persists after iframe reload

Medium Severity

The reload() method resets formData to empty but does not reset lastClickedButton. Similarly, the propInboxQuickFill watcher triggers an iframe reload without clearing lastClickedButton. If a user clicked a button before the reload, the stale button info remains and could be used as the fallback when the form is submitted after reload, potentially reporting the wrong button action for the inbox rule.

Additional Locations (1)

Fix in Cursor Fix in Web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants